home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Night Owl 6
/
Night Owl's Shareware - PDSI-006 - Night Owl Corp (1990).iso
/
001a
/
bkla104.zip
/
BINKLA.DOC
next >
Wrap
Text File
|
1991-04-22
|
25KB
|
513 lines
BinkLA Version 1.04
April 22nd ,1991
╔═══════════════════════╤═════════════════════╤═══════════════════════╗
║▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ BinkLA Version 1.04 │▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓║
╠═══════════════════════╧═════════════════════╧═══════════════════════╣
║ Binkley Log Level 5 Analyzer ║
║ Copyright (C) 1991 by R.J. (Bob) Ross - ALL RIGHTS RESERVED ║
║ SysOp of RJ's Byteline BBS - FidoNet 1:134/75 ║
╙─────────────────────────────────────────────────────────────────────╜
- 1 -
──────── What Is BinkLA ────────
BinkLA is a program I wrote to look at the Binkley Log file. It's
prime purpose is to summarize output on Network activity. The
information reported is obtained from string information contained in a
BinkleyTerm log file.
──────── Acknowledgement ───────
BinkleyTerm is Copyright by Robert Hartman and Vincent Perriello. QSort
if Copyright by Ben Baker. I claim no credit for any part of this
fine software. I hope my BinkLA program will compliment BinkleyTerm by
summarizing the log entries.
────────── Why BinkLA ──────────
I wrote BinkLA for my own use when I was humping and Hubing mail/files
around Fido Net 1:163. I found it gave a great view of what was going
on in my system. Other SysOps in Net 1:163 expressed interest. I've
been making progressive improvements ever since. The first official
release of BinkLA (Version 1.00) was distributed by SDS in early March,
1990.
────── Where to Put BinkLA ─────
I recommend that BinkLA reside in the same directory as your Binkley
executables and log file however this is not a mandatory requirement.
Some other points:
(2) The Binkley log file may be called any valid DOS file name and
may reside in any directory. Please see "How to Run BinkLA"
on the next page. LogLevel must be set at five (5) in the
Binkley.Cfg file to obtain accurate results.
(3) Either QSort or the DOS Sort.Exe utility MUST be available on
your path or reside in that same directory that BinkLA is run
from. BinkLA will look for QSort as a default. If it does not
find QSort on your path or home directory it will fall back
to using DOS Sort.Exe. I highly recommend using QSort as
it's a lot faster and uses a less memory to sort.
╔═══════════════════════╤═════════════════════╤═══════════════════════╗
║▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ BinkLA Version 1.04 │▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓║
╠═══════════════════════╧═════════════════════╧═══════════════════════╣
║ Binkley Log Level 5 Analyzer ║
║ Copyright (C) 1991 by R.J. (Bob) Ross - ALL RIGHTS RESERVED ║
║ SysOp of RJ's Byteline BBS - FidoNet 1:134/75 ║
╙─────────────────────────────────────────────────────────────────────╜
- 2 -
────── When to run BinkLA ──────
You can run BinkLA several times a day if you like. One very good time
to run it would be during a daily maintenance event. I suggest you
start a new Binkley.log every 24 hours. I append BKLARPT.TXT to my
Binkley.log file just before I run my nightly SavLogs program.
─────── How to run BinkLA ──────
Use:
BINKLA [<-switch> <LOG=log filename>] or
BINKLA [@filename[.rsp]]
All switches are optional as is the log filename and may be given in
any order. If no Command Line parameters are given BinkLA. Defaults to
creating BKLARPT.TXT and uses Binkley.log in the default directory.
Switches:
No switch will use the default log called Binkley.log, produce
Bklarpt.txt and exit BinkLA
-BBS Will produce file BKLARPT.BBS, an Ansi colourized version of
BKLARPT.TXT suitable for display on a BBS system. The file
contains a clear screen (ASCII Value 12) and more prompt
(ASCII Value 5) code at the beginning of the file. This works
well with my Maximus BBS setup. I don't know what affect
it will have on other BBS systems. Use and 'Kludge' at your
own discretion. If you use Maximus using Video IBM, Maximus
will display the raw ANSI codes on the local screen but users
won't see them.
-D Optional -Ddrive:\path\filename.ext will produce a data file
from the data gathered to produce Part I of the BinkLA report
The fields are delimited by commas (,). The field
descriptions are: Zone, Net, Node, Calls_Out, Connect,
Calls_In, Msg_Bytes_Outgoing, Msg_Bytes_Incoming, CPS_Avg,
Transfer_Seconds. If no Zone information is available, the
Zone field will be padded as 99. If no filename is given with
the -D switch, the default filename will be Bklarpt.Dat.
-EX. Suppress filenames (-EX.Ext.Ext.Ext) in Part II of
Bklarpt.txt or .bbs. Example: Binkla -EX.TIC.RSP.REQ will
suppress all incoming/outgoing filenames with an extension of
TIC, RSP or REQ. A Maximum of 10 .Ext parameters may be used
with the -EX switch.
-H A brief help screen.
╔═══════════════════════╤═════════════════════╤═══════════════════════╗
║▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ BinkLA Version 1.04 │▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓║
╠═══════════════════════╧═════════════════════╧═══════════════════════╣
║ Binkley Log Level 5 Analyzer ║
║ Copyright (C) 1991 by R.J. (Bob) Ross - ALL RIGHTS RESERVED ║
║ SysOp of RJ's Byteline BBS - FidoNet 1:134/75 ║
╙─────────────────────────────────────────────────────────────────────╜
- 3 -
-L Will cause BinkLA to read the Binkley log file entries,
produce text file BKLARPT.TXT and display the output to the
screen using a list procedure. The list procedure allows full
forward/backward scroll, Pg Up, Pg Dn, End, Esc, Home and
eXit. A maximum of 225 report output text lines are supported
by the list procedure.
-LL If file BKLARPT.TXT exists in the default directory, BinkLA
will immediately jump to the list procedure and display the
last created BKLARPT.TXT. Note: if any other command line
switches are given with the -LL switch, they will be ignored.
-NZ Will suppress Zone information and only display Net/Node in
Bklarpt. This should make Binkla 1.04 and above compatible
with BinkleyTerm Version 1.30
LOG= Log=[path\]filename may be used to read a Binkley.log in
another directory and/or a logfile not called the default
"Binkley.log".
@ @filename[.rsp] may be used instead of using the switches on
the Command line. The response file must be in text format
and have an extension of ".RSP". When calling the response
file from the command line the extension may be omitted as
.RSP is assumed. ie: BINKLA @BLA1 would look in the current
directory for a file called BLA1.RSP. The purpose of the
response file is to make it easier to execute BinkLA using
multiple switches. For example instead of - BINKLA -L -NZ
-EX.TIC.REQ LOG=System.log which is quite cumbersome to type
from the command line you can create a plain text file
containing the command line parameters. BinkLA only reads the
first line of the of the response file so you may include any
remarks on subsequent lines if you like.
─────── Explanatory Notes ──────
Log File Strings.
BinkLA uses the following strings found in a Binkley log file:
" Timeout"
"BINK Too many errors"
"BINK begin"
"BINK Connect 1200"
"BINK Connect 2400"
"BINK Connect 9600"
"BINK CPS:"
"BINK Disconnecting nuisance"
"BINK End of connection attempt"
"BINK End of FTS-000"
"BINK End of WaZOO"
"BINK end,"
"BINK Exiting to BBS"
╔═══════════════════════╤═════════════════════╤═══════════════════════╗
║▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ BinkLA Version 1.04 │▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓║
╠═══════════════════════╧═════════════════════╧═══════════════════════╣
║ Binkley Log Level 5 Analyzer ║
║ Copyright (C) 1991 by R.J. (Bob) Ross - ALL RIGHTS RESERVED ║
║ SysOp of RJ's Byteline BBS - FidoNet 1:134/75 ║
╙─────────────────────────────────────────────────────────────────────╜
- 4 -
"BINK Inbound"
"BINK Incoming cal"
"BINK Incoming call, dial aborted"
"BINK No Send"
"BINK Nobody answered"
"BINK Nothing to send"
"BINK Password override for outgoing call"
"BINK Processing node"
"BINK Pwd Err"
"BINK Password Err"
"BINK Received"
"BINK Remote didn't respond
"BINK Resuming from offset"
"BINK Synchronizing to Offset"
"BINK Spawning BBS"
"BINK Z-rz Too many errors"
"BINK Z-rz ???"
"Ring"
"SpawnBBS"
If any of these strings are changed in the Binkley.lng file, chances
are that BinkLA will run with erroneous results.
System Name.
If BinkLA finds a Binkley.Cfg file in the default directory, it will
parse the Binkley.Cfg file looking for the "System" verb and display
the BBS name of the System at the top (center) of the BinkLA report
(BKLARPT.TXT).
Time periods.
BinkLA gets it's start time period from the first begin statement.
Ending time comes from the last end statement. Version 1.00 was
dependent on a begin statement from the log file.
I was informed that Point operation of Binkley without a Nodelist does
not produce a begin statement in the log. Begin statement dependence
has been removed from Version 1.01. If BinkLA does not find it or an
end time it will create a pseudo time and continue processing.
Telephone Calls (Part I).
Telephone calls where a file transfer occurs are not tabulated in Part
I. Unsuccessful connect attempts will tabulate in Part I even though
the attempt might be to send a file.
Transfer Minutes (Part I).
Transfer minutes is based on the the formula (Bytes Transferred / CPS)
/ 60 rounded for output to one decimal point accuracy.
╔═══════════════════════╤═════════════════════╤═══════════════════════╗
║▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ BinkLA Version 1.04 │▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓║
╠═══════════════════════╧═════════════════════╧═══════════════════════╣
║ Binkley Log Level 5 Analyzer ║
║ Copyright (C) 1991 by R.J. (Bob) Ross - ALL RIGHTS RESERVED ║
║ SysOp of RJ's Byteline BBS - FidoNet 1:134/75 ║
╙─────────────────────────────────────────────────────────────────────╜
- 5 -
Average CPS (Part I).
Average CPS is calculated by dividing the transfer time (seconds) into
the total number of bytes transferred.
CPS Rate (Part II).
The CPS rate is the actual rate shown in the Log. The Total column CPS
Rate is an average of the of the total CPS Rate / File Transfers.
Totals (Part II).
The totals in Part II are:
(1) The total number of files transferred.
(2) Total bytes sent.
(3) Total bytes received.
(4) An average CPS transfer rate.
(5) Total transfer minutes.
Unsuccessful Connect Attempts (Part III)
Unsuccessful Connect Attempts are (Calls Out plus Calls In) minus
connects.
─────────── Bug Reports ────────
The program is VERY string intensive. I have been collecting the
strings that occur in my Log and injecting them into BinkLA when
discrepancies occur. I don't know if I have managed to capture every
different occurrence.
For those of you who sent suggestions and logfiles, thank you. I have
moved to Calgary, Alberta, CANADA and may now be contacted at FidoNet
Node 1:134/75
A special thanks go out to Ken Wilson (1:163/211) for doing extensive
Beta testing and providing suggested improvements during my initial
development of BinkLA. And with my recent move to Calgary and Net 134
thanks go out to Tim Bellaart (134/17), Jerry Driscoll (134/30), Cary
Belger (134/33), Warren Sealock (134/42), Gred Belanger (134/48) and
Joe Lindstrom (134/55) who all helped me Beta test V1.03 using Binkley
V2.40.
──────────── Releases ──────────
BinkLA Version 1.00 released March 3rd, 1990.
BinkLA Version 1.01 released April 16th, 1990.
╔═══════════════════════╤═════════════════════╤═══════════════════════╗
║▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ BinkLA Version 1.04 │▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓║
╠═══════════════════════╧═════════════════════╧═══════════════════════╣
║ Binkley Log Level 5 Analyzer ║
║ Copyright (C) 1991 by R.J. (Bob) Ross - ALL RIGHTS RESERVED ║
║ SysOp of RJ's Byteline BBS - FidoNet 1:134/75 ║
╙─────────────────────────────────────────────────────────────────────╜
- 5 -
BinkLA Version 1.02 released April 21st, 1990.
This version adds an additional string search and allows for longer
Net/Node numbers. Also, at least one statement in the program could get
confused if a Log file line other than a Binkley log file appeared in
the Log. This bug has been corrected.
BinkLA Version 1.03 released December 12th, 1990
With the release of BinkleyTerm V2.40, the Zone number will now appear
in the BinkLA report output if the information is available in the log
entry used by BinkLA. I've found that if you Poll your Boss Node using
ALT-Y in Binkley, the Zone number does not appear in the log file and
will therefore not appear in BinkLA report output for that Node.
Domain addressing (eg @fidonet.org) caused some problems with V1.02 as
well. I hope that I have corrected this problem but would really like
to test a few more Binkley.log files using this feature in Binkley
2.40. If domain addressing is used in the Binkley log file, BinkLA
will suppress it.
I've had some difficulty dealing with Janus transfers. I hope I have
it right. Basically I look at each individual transfer and disregard
the overall total transfer statistics.
BinkLA Version 1.04 released 22 April, 1991
Binkla 1.04 started Beta test as of December 26th, 1990. Somebody in
one of the Echos said that "A good program is never finished". BinkLA
must be a good program. :-).
This version changes the command line parser and adds switches
-D<drive:\path\filename.ext, -EX.ext.ext... -NZ, LOG=[path\]filename
(syntax change) and @ResponseFile. 1.04 also incorporates the string
"Synchronizing from Offset" and 'Remote didn't respond'.
The Average CPS rate algorithm has been changed in Bklarpt to more
accurately reflect the overall average transfer rates. Thanks go out
to Bob Davis of FidoNet 1:106/114 for sending me Logs and raising an
observation on the CPS transfer rate.
The global error exit routine has been re-written to attempt to better
describe the error in the event that BinkLA crashes. However, if a DOS
error occurs while QSort or Sort are executing external to BinkLA the
global error routine may not reflect the true occurrence of the event.
For example if an "Input past end of file" error is indicated this
could mean that your disk is full or there is not enough available
memory in your system for BinkLA to write it's temporary sort file
while out doing a sort. These are the only two obscure errors that I
have observed but there may be others.
Fixed a problem with erronious data being reported when Binkley is in
terminal mode.
╔═══════════════════════╤═════════════════════╤═══════════════════════╗
║▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│ BinkLA Version 1.04 │▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓║
╠═══════════════════════╧═════════════════════╧═══════════════════════╣
║ Binkley Log Level 5 Analyzer ║
║ Copyright (C) 1991 by R.J. (Bob) Ross - ALL RIGHTS RESERVED ║
║ SysOp of RJ's Byteline BBS - FidoNet 1:134/75 ║
╙─────────────────────────────────────────────────────────────────────╜
- 6 -
Shortened Column Length
I shortened the width of the output report from 77 columns to 76
columns to cure a wrapping problem with QuickBBS when the output is
placed in a message.
Fixed a couple BUGS
If BinkLA now runs out of disk space while processing it's work files,
it will now graciously(?) exit to DOS.
With an observation from the NEC of 134 - Joe Lindstrom, I bagged
another BUG when "Synchronizing to Offset" occurred. This was a logic
error on my part in the program. I corrected it and hope that no
undesirable results spin off at a result of the change I made.
─────────── Conclusion ─────────
BinkLA is supplied as is. Users are granted unlimited free license for
it's use. It's my small donation to the BBS community and hobby.
I would be very pleased if you took the time to to try BinkLA on your
system. I've had some very good vibes from Sysops around the world
using BinkLA and I'm pleased that I am able to dedicate a worthwhile
program freely given in the same spirit as BinkleyTerm.
One thing I would very much appreciate is if you would send me a
NetMail message to FidoNet 1:134/75 to let me know if you use the
program. I have a world map on my wall and I would very much like to
stick a few map pins in it to indicate BBS friends from other places
who are using my program. Or you can drop me a Post Card via Snail Mail
to:
R.J. (Bob) Ross
#107A 3730 50th Street N.W.
Calgary, Alberta, Canada
T3A 2V9
I hope you enjoy the program. A sample output report follows.
Yours truly,
R.J. (Bob) Ross
─────── An Example Output ──────
BINKLEY.LOG BinkLA V1.04
RJ's Byteline BBS
Binkley Log Statistics for the period of
04 Feb 03:10:38 Hrs «« to »» 04 Feb 22:35:39 Hrs
┌──────────────────┬────────────────────────────────────┬──────────────────┐
│░░░░░░░░░░░░░░░░░░│ Part I - Message Transfers & Calls │░░░░░░░░░░░░░░░░░░│
╞══════════════╤═══╧════════════════╤═══════════════════╧═════╤══════╤═════╡
│Zone:Net/Node │ Telephone Calls │ Message Bytes │ CPS │ Tran│
│ Number │ Out │ Connect │ In │ Outgoing │ Incoming │ Avg │ Min│
╞══════════════╧═════╧═════════╧════╧════════════╧════════════╧══════╧═════╡
│1:134/0 25 4 3 862 5,229 210 0.5│
│1:134/1 27 4 1 3,153 139,350 1025 2.3│
│1:134/2 5 6 5 2,386 30,296 229 2.4│
│1:134/55 1 2 1 1,348 1,248 371 0.1│
│1:30124/1 0 5 5 108,226 4,715 230 8.2│
├──────────────────────────────────────────────────────────────────────────┤
│ TOTALS 58 21 15 115,975 180,838 366 13.5│
╘══════════════════════════════════════════════════════════════════════════╛
┌───────────────────┬──────────────────────────────────┬───────────────────┐
│░░░░░░░░░░░░░░░░░░░│ PART II - Network File Transfers │░░░░░░░░░░░░░░░░░░░│
╞══════════════╤════╧═══════════════╤══════════════════╧══════╤══════╤═════╡
│Zone:Net/Node │ │ File Bytes │ CPS │ Tran│
│ Number │ File Names │ Outgoing │ Incoming │ Rate │ Min│
╞══════════════╧════════════════════╧════════════╧════════════╧══════╧═════╡
│1:134/55 0086004B.REQ 0 55 55 0.0│
│1:134/55 0086004B.REQ 0 74 74 0.0│
│1:134/55 0086004B.REQ 0 94 31 0.1│
│1:134/55 0086004B.RSP 921 0 307 0.1│
│1:134/55 0086004B.RSP 968 0 242 0.1│
│1:134/55 0086004B.RSP 968 0 322 0.1│
│1:134/55 ADVBAS9A.LZH 126,922 0 1048 2.0│
│1:134/55 BAS-SORT.LZH 40,949 0 1049 0.6│
│1:134/55 BASDEMO.LZH 355,848 0 985 6.0│
│1:134/55 BASICDIR.LZH 75,325 0 1091 1.1│
│1:134/55 BASWIZ12.LZH 118,813 0 1100 1.8│
│1:134/55 BDISK.LZH 17,942 0 996 0.3│
│1:134/55 COMPILE7.LZH 139,622 0 1099 2.1│
│1:134/55 FASTBAS.LZH 5,816 0 830 0.1│
│1:134/55 FILELIST.LZH 32,502 0 928 0.6│
│1:134/55 WINDEZ34.LZH 133,948 0 1107 2.0│
├──────────────────────────────────────────────────────────────────────────┤
│ TOTALS 16 1,050,544 223 1029 17.0│
╘══════════════════════════════════════════════════════════════════════════╛
┌──────────────────────────┬────────────────────┬──────────────────────────┐
│░░░░░░░░░░░░░░░░░░░░░░░░░░│ PART III - SUMMARY │░░░░░░░░░░░░░░░░░░░░░░░░░░│
╞══════════════════════════╧════╤═══════════════╧══════════════════════════╡
│ BBS Callers at 9600 = 0 │ Message Bytes Transferred = 296,813 │
│ 2400 = 0 │ File Bytes Transferred = 1,050,767 │
│ 1200 = 0 │ TOTAL Bytes Transferred = 1,347,580 │
│ Other = 0 ├──────────────────────────────────────────┤
│ │ Message Connect Time = 0.2 │
│ TOTAL BBS Callers = 0 │ File Transfer Connect Time = 0.3 │
│ │ TOTAL Connect Time (Hours) = 0.5 │
│ ├──────────────────────────────────────────┤
│ │ Unsuccessful Connect Attempts= 52 │
└───────────────────────────────┴──────────────────────────────────────────┘
Created Data File: BKLARPT.DAT
Sample BKLARPT.DAT
1,134,0,25,4,3,862,5229,210.0345,29
1,134,1,27,4,1,3153,139350,1025.201,139
1,134,2,5,6,5,2386,30296,228.5455,143
1,134,55,1,2,1,1348,1248,370.8571,7
1,30124,1,0,5,5,108226,4715,229.5549,492